Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0140

reference: 184-tree-1
name: 0140
tree-preservation-order: undefined
184-tpo-1
uprn
address-text
point: POINT (-0.937207 50.865586)
geometry: MULTIPOLYGON (((-0.937122 50.865577,-0.937126 50.865594,-0.937138 50.865609,-0.937156 50.865621,-0.937180 50.865629,-0.937206 50.865632,-0.937233 50.865629,-0.937257 50.865622,-0.937276 50.865610,-0.937288 50.865595,-0.937293 50.865578,-0.937289 50.865562,-0.937277 50.865547,-0.937259 50.865534,-0.937235 50.865527,-0.937209 50.865524,-0.937182 50.865526,-0.937158 50.865533,-0.937139 50.865545,-0.937127 50.865560,-0.937122 50.865577)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL